Wireless Communications And Power Configurations

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. A wireless device may receive at least one power configuration parameter from a base station. The at least one power configuration parameter may be based on information that the wireless device sends to the base station.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. application Ser. No.16/277,110, titled “Wireless Communications and Power Configurations”and filed Feb. 15, 2019, which claims the benefit of U.S. ProvisionalApplication No. 62/631,401, titled “UE Information for Distributed Unit”and filed on Feb. 15, 2018. The above-referenced applications are herebyincorporated by reference in their entireties for all purposes.

BACKGROUND

A wireless device may receive at least one configuration parameter, forexample, from a base station, that may result in a variety of issues,for example, inefficient radio resource configuration, increased calldropping, and/or increased radio link failures. It is desired to improvewireless communications without adversely increasing signaling overheadand/or decreasing spectral efficiency.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for wirelesscommunications using wireless device information. A wireless device maysend the wireless device information to a base station, which maycomprise a base station distributed unit and a base station centralunit. The base station central unit may receive the wireless deviceinformation and provide it to the base station distributed unit so thatthe base station distributed unit may determine one or moreconfiguration parameters for the wireless device and/or other wirelessdevices in a cell that are based on the wireless device information. Byusing these one or more configuration parameters, the wireless deviceand/or other wireless devices in the cell may be able to improvewireless communications and/or increase power efficiency.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16 shows an example of messaging associated with wireless deviceinformation.

FIG. 17 shows an example data flow for messaging associated withwireless device information.

FIG. 18 shows an example data flow of messaging associated with wirelessdevice information.

FIG. 19 shows examples of communications between a wireless device and abase station.

FIG. 20 shows an example of configuring a wireless device with one ormore power configuration parameters based on wireless deviceinformation.

FIG. 21 shows an example of providing one or more power configurationparameters that may be performed by a base station distributed unit.

FIG. 22 shows an example of providing one or more power configurationparameters that may be performed by a base station central unit.

FIG. 23 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto wireless communication systems in multicarrier communication systems.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

-   -   3GPP 3rd Generation Partnership Project    -   5GC 5G Core Network    -   ACK Acknowledgement    -   AMF Access and Mobility Management Function    -   ARQ Automatic Repeat Request    -   AS Access Stratum    -   ASIC Application-Specific Integrated Circuit    -   BA Bandwidth Adaptation    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   BPSK Binary Phase Shift Keying    -   BWP Bandwidth Part    -   CA Carrier Aggregation    -   CC Component Carrier    -   CCCH Common Control CHannel    -   CDMA Code Division Multiple Access    -   CN Core Network    -   CP Cyclic Prefix    -   CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex    -   C-RNTI Cell-Radio Network Temporary Identifier    -   CS Configured Scheduling    -   CSI Channel State Information    -   CSI-RS Channel State Information-Reference Signal    -   CQI Channel Quality Indicator    -   CSS Common Search Space    -   CU Central Unit    -   DC Dual Connectivity    -   DCCH Dedicated Control Channel    -   DCI Downlink Control Information    -   DL Downlink    -   DL-SCH Downlink Shared CHannel    -   DM-RS DeModulation Reference Signal    -   DRB Data Radio Bearer    -   DRX Discontinuous Reception    -   DTCH Dedicated Traffic Channel    -   DU Distributed Unit    -   EPC Evolved Packet Core    -   E-UTRA Evolved UMTS Terrestrial Radio Access    -   E-UTRAN Evolved-Universal Terrestrial Radio Access Network    -   FDD Frequency Division Duplex    -   FPGA Field Programmable Gate Arrays    -   F1-C F1-Control plane    -   F1-U F1-User plane    -   gNB next generation Node B    -   HARQ Hybrid Automatic Repeat reQuest    -   HDL Hardware Description Languages    -   IE Information Element    -   IP Internet Protocol    -   LCID Logical Channel Identifier    -   LTE Long Term Evolution    -   MAC Media Access Control    -   MCG Master Cell Group    -   MCS Modulation and Coding Scheme    -   MeNB Master evolved Node B    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MN Master Node    -   NACK Negative Acknowledgement    -   NAS Non-Access Stratum    -   NG CP Next Generation Control Plane    -   NGC Next Generation Core    -   NG-C NG-Control plane    -   ng-eNB next generation evolved Node B    -   NG-U NG-User plane    -   NR New Radio    -   NR MAC New Radio MAC    -   NR PDCP New Radio PDCP    -   NR PHY New Radio PHYsical    -   NR RLC New Radio RLC    -   NR RRC New Radio RRC    -   NSSAI Network Slice Selection Assistance Information    -   O&M Operation and Maintenance    -   OFDM Orthogonal Frequency Division Multiplexing    -   PBCH Physical Broadcast CHannel    -   PCC Primary Component Carrier    -   PCCH Paging Control CHannel    -   PCell Primary Cell    -   PCH Paging CHannel    -   PDCCH Physical Downlink Control CHannel    -   PDCP Packet Data Convergence Protocol    -   PDSCH Physical Downlink Shared CHannel    -   PDU Protocol Data Unit    -   PHICH Physical HARQ Indicator CHannel    -   PHY PHYsical    -   PLMN Public Land Mobile Network    -   PMI Precoding Matrix Indicator    -   PRACH Physical Random Access CHannel    -   PRB Physical Resource Block    -   PSCell Primary Secondary Cell    -   PSS Primary Synchronization Signal    -   pTAG primary Timing Advance Group    -   PT-RS Phase Tracking Reference Signal    -   PUCCH Physical Uplink Control CHannel    -   PUSCH Physical Uplink Shared CHannel    -   QAM Quadrature Amplitude Modulation    -   QFI Quality of Service Indicator    -   QoS Quality of Service    -   QPSK Quadrature Phase Shift Keying    -   RA Random Access    -   RACH Random Access CHannel    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RA-RNTI Random Access-Radio Network Temporary Identifier    -   RB Resource Blocks    -   RBG Resource Block Groups    -   RI Rank indicator    -   RLC Radio Link Control    -   RRC Radio Resource Control    -   RS Reference Signal    -   RSRP Reference Signal Received Power SCC Secondary Component        Carrier    -   SCell Secondary Cell    -   SCG Secondary Cell Group    -   SC-FDMA Single Carrier-Frequency Division Multiple Access    -   SDAP Service Data Adaptation Protocol    -   SDU Service Data Unit    -   SeNB Secondary evolved Node B    -   SFN System Frame Number    -   S-GW Serving GateWay    -   SI System Information    -   SIB System Information Block    -   SMF Session Management Function    -   SN Secondary Node    -   SpCell Special Cell    -   SRB Signaling Radio Bearer    -   SRS Sounding Reference Signal    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   sTAG secondary Timing Advance Group    -   TA Timing Advance    -   TAG Timing Advance Group    -   TAI Tracking Area Identifier    -   TAT Time Alignment Timer    -   TB Transport Block    -   TC-RNTI Temporary Cell-Radio Network Temporary Identifier    -   TDD Time Division Duplex    -   TDMA Time Division Multiple Access    -   TTI Transmission Time Interval    -   UCI Uplink Control Information    -   UE User Equipment    -   UL Uplink    -   UL-SCH Uplink Shared CHannel    -   UPF User Plane Function    -   UPGW User Plane Gateway    -   VHDL VHSIC Hardware Description Language    -   Xn-C Xn-Control plane    -   Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, and/or the like. Physical radio transmission may be enhanced bydynamically or semi-dynamically changing the modulation and codingscheme, for example, depending on transmission requirements and/or radioconditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., an gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Media Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. Mapping restrictions in alogical channel prioritization may control which numerology and/ortransmission timing a logical channel may use. An RLC sublayer maysupport transparent mode (TM), unacknowledged mode (UM), and/oracknowledged mode (AM) transmission modes. The RLC configuration may beper logical channel with no dependency on numerologies and/orTransmission Time Interval (TTI) durations. Automatic Repeat Request(ARQ) may operate on any of the numerologies and/or TTI durations withwhich the logical channel is configured. Services and functions of thePDCP layer for the user plane may comprise, for example, sequencenumbering, header compression and decompression, transfer of user data,reordering and duplicate detection, PDCP PDU routing (e.g., such as forsplit bearers), retransmission of PDCP SDUs, ciphering, deciphering andintegrity protection, PDCP SDU discard, PDCP re-establishment and datarecovery for RLC AM, and/or duplication of PDCP PDUs. Services and/orfunctions of SDAP may comprise, for example, mapping between a QoS flowand a data radio bearer. Services and/or functions of SDAP may comprisemapping a Quality of Service Indicator (QFI) in DL and UL packets. Aprotocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel. Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCID for alogical channel and/or MAC CE may be configured for the wireless deviceby the base station. The MAC sub-header corresponding to a MAC CE and/ora MAC SDU may comprise an LCID associated with the MAC CE and/or the MACSDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands. The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MA CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs indicating one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by 5GC; paging for mobile terminateddata area managed by 5GC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterInformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signaling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random-accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., only static capabilitiesmay be stored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A, FIG. 7B,FIG. 8, and associated text, described below.

Other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a Wi-Fi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. An CP-OFDM signal for uplinktransmission may be generated by FIG. 4A, for example, if transformprecoding is not enabled. These functions are shown as examples andother mechanisms may be implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;doppler spread; doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least an MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be fewer than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel. The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SSB/PBCH, for example,if the downlink CSI-RS 522 and SSB/PBCH are spatially quasi co-locatedand resource elements associated with the downlink CSI-RS 522 areoutside of the PRBs configured for the SSB/PBCH.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time for acarrier. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers (such as forcarrier aggregation) or ranging from 1 to 64 carriers (such as for dualconnectivity). Different radio frame structures may be supported (e.g.,for FDD and/or for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. Radio frame duration may be 10 milliseconds (ms). A 10 msradio frame 601 may be divided into ten equally sized subframes 602,each with a 1 ms duration. Subframe(s) may comprise one or more slots(e.g., slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Other subframe durations such as, for example, 0.5 ms, 1 ms, 2ms, and 5 ms may be supported. Uplink and downlink transmissions may beseparated in the frequency domain. Slot(s) may include a plurality ofOFDM symbols 604. The number of OFDM symbols 604 in a slot 605 maydepend on the cyclic prefix length. A slot may be 14 OFDM symbols forthe same subcarrier spacing of up to 480 kHz with normal CP. A slot maybe 12 OFDM symbols for the same subcarrier spacing of 60 kHz withextended CP. A slot may comprise downlink, uplink, and/or a downlinkpart and an uplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size ofan RBG may depend on at least one of: an RRC message indicating an RBGsize configuration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

a base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) a DCI via aPDCCH addressed to a Configured Scheduling-RNTI (CS-RNTI) activating theCS resources. The DCI may comprise parameters indicating that thedownlink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC messages.The CS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) a DCI via a PDCCH addressed to a CS-RNTI toactivate the CS resources. The DCI may comprise parameters indicatingthat the uplink grant is a CS grant. The CS grant may be implicitlyreused according to the periodicity defined by the one or more RRCmessage, The CS grant may be implicitly reused, for example, untildeactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more transport blocks. TheDCI may indicate a downlink assignment indicating parameters forreceiving one or more transport blocks. The DCI may be used by the basestation to initiate a contention-free random access at the wirelessdevice. The base station may send (e.g., transmit) a DCI comprising aslot format indicator (SFI) indicating a slot format. The base stationmay send (e.g., transmit) a DCI comprising a pre-emption indicationindicating the PRB(s) and/or OFDM symbol(s) in which a wireless devicemay assume no transmission is intended for the wireless device. The basestation may send (e.g., transmit) a DCI for group power control of thePUCCH, the PUSCH, and/or an SRS. A DCI may correspond to an RNTI. Thewireless device may obtain an RNTI after or in response to completingthe initial access (e.g., C-RNTI). The base station may configure anRNTI for the wireless (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, TPC-SRS-RNTI). The wireless device may determine (e.g.,compute) an RNTI (e.g., the wireless device may determine the RA-RNTIbased on resources used for transmission of a preamble). An RNTI mayhave a pre-configured value (e.g., P-RNTI or SI-RNTI). The wirelessdevice may monitor a group common search space which may be used by thebase station for sending (e.g., transmitting) DCIs that are intended fora group of wireless devices. A group common DCI may correspond to anRNTI which is commonly configured for a group of wireless devices. Thewireless device may monitor a wireless device-specific search space. Awireless device specific DCI may correspond to an RNTI configured forthe wireless device.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel. The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain. In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a wireless device is configured with a secondary carrier on a primarycell, the wireless device may be configured with an initial BWP forrandom access procedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base statin may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may not configure awireless device without a common search space on a PCell, or on aPSCell, in an active DL BWP. For an UL BWP in a set of one or more ULBWPs, a base station may configure a wireless device with one or moreresource sets for one or more PUCCH transmissions.

A DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided a default DL BWP, a default BWP may be an initialactive DL BWP.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects a DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects a DCI indicating anactive DL BWP or UL BWP, other than a default DL BWP or UL BWP, for anunpaired spectrum operation. The wireless device may increment the timerby an interval of a first value (e.g., the first value may be 1millisecond, 0.5 milliseconds, or any other time duration), for example,if the wireless device does not detect a DCI at (e.g., during) theinterval for a paired spectrum operation or for an unpaired spectrumoperation. The timer may expire at a time that the timer is equal to thetimer value. A wireless device may switch to the default DL BWP from anactive DL BWP, for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving aDCI indicating the second BWP as an active BWP, and/or after or inresponse to an expiry of BWP inactivity timer (e.g., the second BWP maybe a default BWP). FIG. 10 shows an example of three BWPs configured,BWP1 (1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020and 1040) may be a default BWP. BWP1 (1010) may be an initial activeBWP. A wireless device may switch an active BWP from BWP1 1010 to BWP21020, for example, after or in response to an expiry of the BWPinactivity timer. A wireless device may switch an active BWP from BWP21020 to BWP3 1030, for example, after or in response to receiving a DCIindicating BWP3 1030 as an active BWP. Switching an active BWP from BWP31030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be after or inresponse to receiving a DCI indicating an active BWP, and/or after or inresponse to an expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be deactivated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and secondarybase station(s) for multi-connectivity, one or more of the following maybe used. A master base station and/or a secondary base station maymaintain RRM measurement configurations of a wireless device. A masterbase station may determine (e.g., based on received measurement reports,traffic conditions, and/or bearer types) to request a secondary basestation to provide additional resources (e.g., serving cells) for awireless device. After or upon receiving a request from a master basestation, a secondary base station may create and/or modify a containerthat may result in a configuration of additional serving cells for awireless device (or decide that the secondary base station has noresource available to do so). For a wireless device capabilitycoordination, a master base station may provide (e.g., all or a part of)an AS configuration and wireless device capabilities to a secondary basestation. A master base station and a secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried via Xn messages. Asecondary base station may initiate a reconfiguration of the secondarybase station existing serving cells (e.g., PUCCH towards the secondarybase station). A secondary base station may decide which cell is aPSCell within a SCG. A master base station may or may not change contentof RRC configurations provided by a secondary base station. A masterbase station may provide recent (and/or the latest) measurement resultsfor SCG cell(s), for example, if an SCG addition and/or an SCG SCelladdition occurs. A master base station and secondary base stations mayreceive information of SFN and/or subframe offset of each other from anOAM and/or via an Xn interface (e.g., for a purpose of DRX alignmentand/or identification of a measurement gap). Dedicated RRC signaling maybe used for sending required system information of a cell as for CA, forexample, if adding a new SCG SCell, except for an SFN acquired from anMIB of a PSCell of a SCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a MAC entity, and/or a beam failure indication may initiate arandom access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating equivalent and/orsimilar content(s) of Msg1 1220 and Msg3 1240 of a four-step randomaccess procedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for beam failurerecovery request and corresponding PRACH resource(s) (e.g., if any), atime window to monitor RA response(s), a time window to monitorresponse(s) on beam failure recovery request, and/or a contentionresolution timer.

The Msg1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for beam failurerecovery request associated with at least one of SS blocks and/orCSI-RSs. A wireless device may select a random access preamble indexcorresponding to a selected SS block or a CSI-RS from a set of one ormore random access preambles for beam failure recovery request, forexample, if at least one of the SS blocks with an RSRP above a firstRSRP threshold amongst associated SS blocks is available, and/or if atleast one of CSI-RSs with a RSRP above a second RSRP threshold amongstassociated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. The wireless device may select a random access preambleindex, for example, if a base station does not configure a wirelessdevice with at least one contention free PRACH resource associated withSS blocks or CSI-RS. The wireless device may select the at least one SSblock and/or select a random access preamble corresponding to the atleast one SS block, for example, if a base station configures thewireless device with one or more contention free PRACH resourcesassociated with SS blocks and/or if at least one SS block with a RSRPabove a first RSRP threshold amongst associated SS blocks is available.The wireless device may select the at least one CSI-RS and/or select arandom access preamble corresponding to the at least one CSI-RS, forexample, if a base station configures a wireless device with one or morecontention free PRACH resources associated with CSI-RSs and/or if atleast one CSI-RS with a RSRP above a second RSPR threshold amongst theassociated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine an PRACH occasion from oneor more PRACH occasions corresponding to a selected SS block, forexample, if the wireless device selects an SS block and is configuredwith an association between one or more PRACH occasions and/or one ormore SS blocks. The wireless device may determine a PRACH occasion fromone or more PRACH occasions corresponding to a selected CSI-RS, forexample, if the wireless device selects a CSI-RS and is configured withan association between one or more PRACH occasions and one or moreCSI-RSs. The wireless device may send (e.g., transmit), to a basestation, a selected random access preamble via a selected PRACHoccasions. The wireless device may determine a transmit power for atransmission of a selected random access preamble at least based on aninitial preamble power and a power-ramping factor. The wireless devicemay determine an RA-RNTI associated with a selected PRACH occasion inwhich a selected random access preamble is sent (e.g., transmitted). Thewireless device may not determine an RA-RNTI for a beam failure recoveryrequest. The wireless device may determine an RA-RNTI at least based onan index of a first OFDM symbol, an index of a first slot of a selectedPRACH occasions, and/or an uplink carrier index for a transmission ofMsg1 1220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230. The wireless device may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For beam failurerecovery request, the base station may configure the wireless devicewith a different time window (e.g., bfr-ResponseWindow) to monitorresponse on beam failure recovery request. The wireless device may starta time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) at a startof a first PDCCH occasion, for example, after a fixed duration of one ormore symbols from an end of a preamble transmission. If the wirelessdevice sends (e.g., transmits) multiple preambles, the wireless devicemay start a time window at a start of a first PDCCH occasion after afixed duration of one or more symbols from an end of a first preambletransmission. The wireless device may monitor a PDCCH of a cell for atleast one random access response identified by a RA-RNTI, or for atleast one response to beam failure recovery request identified by aC-RNTI, at a time that a timer for a time window is running.

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention free random accessprocedure is triggered for a beam failure recovery request and if aPDCCH transmission is addressed to a C-RNTI. The wireless device maydetermine that the random access procedure is successfully completed,and may indicate a reception of an acknowledgement for a systeminformation request to upper layers, for example, if at least one randomaccess response comprises only a random access preamble identifier. Thewireless device may stop sending (e.g., transmitting) remainingpreambles (if any) after or in response to a successful reception of acorresponding random access response, for example, if the wirelessdevice has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which an MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for an MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of an MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MACSDUs to one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). A MACentity may handle a random access process (e.g., Random Access Control1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4-stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station.

A base station CU (e.g., gNB-CU) may send (e.g., transmit) wirelessdevice information to a base station DU (e.g., gNB-DU). The base stationCU may provide a bearer configuration information, securityconfiguration information, or wireless device capability information toa base station DU. Inefficient radio resource configuration, increasedcall dropping, and/or increased link failures may occur, for example, ifa base station DU configures radio resources of a cell withoutsufficient information, for example, from one or more wireless devices.Without sufficient information, the base station DU may configurenon-preferred radio resource parameters and/or previously failedresource configuration parameters without wireless device information(e.g., resource preferences information and/or failure information of awireless device). Increased data transmission failures, frequent alldropping, increased link failure, and/or inefficient radio resourceemployment may occur. Radio resource configuration by a base station DUmay benefit from a further enhancement in a communication mechanismbetween a base station CU and a base station DU.

Radio resource configuration efficiency may be improved, for example, ifa base station DU configures radio resource configuration parametersbased on, for example, information from one or more wireless devices.Radio resource configuration may be enhanced, for example, if a basestation DU configures radio resource configuration parameters for one ormore cells and/or one or more wireless devices. Information exchangesbetween a base station CU and a base station DU may be enhanced, forexample, if a base station DU configures radio resources. Informationexchange among a base station CU and a base station DU may be enhanced,for example, to improve radio parameter configuration mechanism if abase station DU configures radio resources. By communicatinginformation, for example, an indication of a preference of the wirelessdevice for one or more power saving configurations (and/or otherwireless device information), from a wireless device to a base station(e.g., a base station DU via a base station CU), advantages may beachieved for the wireless device (and/or for additional wireless devicesthat may communicate with the base station). Such advantages maycomprise, for example, for one or more wireless devices and/or for oneor more cells: more efficient radio resource configurations, reducedpower usage, decreased call dropping, and/or decreased link failures.

A wireless device may configure power parameters for transmissions ofone or more transport blocks. A base station (e.g., a base stationdistributed unit (DU) and/or a base station central unit (CU)) maydetermine one or more power configuration parameters for the wirelessdevice. The wireless device may send (e.g., transmit), to the basestation, wireless device information. The wireless device informationmay comprise an indication of a preference of the wireless device forone or more power saving configurations. The base station may determinethe one or more power configuration parameters for the wireless devicebased on the wireless device information. A base station CU maydetermine the one or more power configuration parameters. The basestation CU may have wireless device information for the wireless deviceand/or a plurality of other wireless devices. The base station CU may beable to determine the one or more power configuration parameters for thewireless device based on wireless device information for the wirelessdevice and/or wireless device information for a plurality of otherwireless devices. A base station DU may receive, from the base stationCU, the one or more power configuration parameters. The base station DUmay update the one or more power configuration parameters. Additionallyor alternatively, the base station DU may determine the one or morepower configuration parameters. The base station DU may receive, fromthe base station CU, the wireless device information (e.g., preferenceof the wireless device for one or more power saving configurations). Thebase station DU may have more recently updated information for thewireless device, such as based on one or more channel state information(CSI) reports, than the base station CU may have. The base station DUmay be able to dynamically adjust power configuration parameters for thewireless device based on the wireless device information and/or CSIreports, measurement reports, and/or the like. Some wireless deviceinformation (e.g., random access report, connection establishment,mobility history, multicast-broadcast single frequency network (MBSFN)measurement, and/or load measurement) for the wireless device may beused to determine one or more power configuration parameters of one ormore other wireless devices. Some wireless device information (e.g.,bandwidth preference, radio link monitoring, and/or delay budget) forthe wireless device may not be used to determine one or more powerconfiguration parameters of one or more other wireless devices. The basestation CU may send a first subset of power configuration parameters tothe wireless device (e.g., via the base station DU). The base station CUmay send a second subset of power configuration parameters to one ormore other wireless devices (e.g., via the base station DU and/or viaone or more other base station DUs).

A base station CU may send (e.g., transmit), to a base station DU,wireless device (e.g., UE) information of a wireless device received viaone or more radio resource control (RRC) messages from the wirelessdevice. Wireless device information may comprise one or more of: randomaccess information, connection establishment failure information, powerpreference information, bandwidth preference information, radio linkmonitoring (RLM) information, delay budget information, loggedmeasurement results, mobility history information, and/or the like. Thebase station DU may configure radio resource parameters for one or morewireless devices based on the wireless device information.

A base station (e.g., a gNB, an eNB, and/or the like) may comprise abase station central unit (CU) (e.g., gNB-CU) and one or more basestation distributed units (DUs) (e.g., gNB-DU). The base station CU mayprovide functionalities of an RRC layer, a PDCP layer, and/or an SDAPlayer for wireless devices. A base station DU of the one or more basestation DUs may provide functionalities of an RLC layer, a MAC layer,and/or a PHY layer for wireless devices. The base station CU may provideone or more upper layers among a PDCP layer, an SDAP layer, an RLClayer, a MAC layer, and/or PHY layer. The base station DU may provideone or more lower layers among a PDCP layer, an SDAP layer, an RLClayer, a MAC layer, and/or PHY layer. The base station CU may beconnected to and/or in communication with the one or more base stationDUs, for example, via one or more F1 interfaces. The base station CU maycommunicate with a base station DU via an F1 interface. The base stationCU and/or the base station DU may serve a wireless device.

FIG. 16 shows an example of messaging associated with wireless deviceinformation. A wireless device 1601 may send (e.g., transmit) a firstradio resource control (RRC) message 1610-A to the base station CU 1603via the base station DU 1602. The first RRC message 1610-A may comprisewireless device information. The wireless device information may beassociated with wireless communications of the wireless device 1601. Thewireless device information may comprise, for example, random accessinformation, connection establishment failure information, powerpreference information, bandwidth preference information, radio linkmonitoring (RLM) information, delay budget information, loggedmeasurement results, mobility history information, and/or the like.After or in response to receiving the first RRC message 1610-A, the basestation DU 1602 may send (e.g., transmit, forward, etc.) a first RRCmessage 1610-B to the base station CU 1603. The first message 1610-B maybe the same message as the first RRC message 1610-A. The wireless device1601 may send (e.g., transmit) the first RRC message (e.g., 1610-A,1610-B) via a signaling radio bearer 1 (e.g., SRB1). The base station DU1602 may not interpret (and/or may not decode) the first RRC message1610-A. The first RRC message (e.g., 1610-A, 1610-B) may comprise awireless device assistance information message (e.g.,UEAssistanceInformation message) and/or a wireless device informationresponse message (e.g., UEInformationResponse message). The base stationDU 1602 may send (e.g., transmit, forward, etc.) the first RRC message1610-B via an F1 interface configured between the base station DU 1602and the base station CU 1603. The base station DU 1602 may send (e.g.,transmit, forward, etc.) the first RRC message 1610-B via a first F1-Cmessage (e.g., in a F1 control plane message). The first RRC message(e.g., 1610-A, 1610-B) may comprise one or more of: an UL RRC messagetransfer message, a wireless device (e.g., UE) context modificationresponse message, a wireless device (e.g., UE) context modificationrequired message, a wireless device (e.g., UE) context modificationfailure message, a wireless device (e.g., UE) context setup responsemessage, a wireless device (e.g., UE) context setup failure message,and/or the like. A first F1-C message may comprise an RRC-Container IE(and/or DU To CU RRC Information IE) comprising the first RRC message(e.g., 1610-A, 1610-B). The first RRC message (e.g., 1610-A, 1610-B) maycomprise a wireless device identifier of the wireless device (e.g.,gNB-CU UE FLAP ID, gNB-DU UE FLAP ID, and/or the like), a signalingradio bearer identifier associated with the first RRC message (e.g., SRBID, which may comprise an integer value from 0 to 3, e.g., SRB1), and/orthe like.

The first RRC message (e.g., 1610-A, 1610-B) may comprise wirelessdevice information of the wireless device 1601. One or more elements ofthe wireless device information may comprise preferences of the wirelessdevice 1601 for radio resource configurations and/or radio resourcestate information collected by the wireless device 1601. The wirelessdevice information may comprise at least one of: a random access reportinformation element (IE) (e.g., rach-Report IE); a connectionestablishment failure report IE (e.g., ConnEstFailReport IE); a powerpreference indication IE (e.g., powerPreflndication IE) indicating thatthe wireless device prefers a configuration for power saving; abandwidth preference IE (e.g., bw-Preference IE); a radio linkmonitoring (RLM) report IE (e.g., rlm-Report IE); a delay budget reportIE (e.g., delayBudgetReport IE) indicating a preferred adjustment toconnected mode discontinuous reception (DRX) or coverage enhancementconfiguration; and/or the like. The wireless device information maycomprise at least one of: a logged measurement report IE (e.g.,logMeasReport IE); a mobility history report IE (e.g.,mobilityHistoryReport IE) indicating at least one time value of stay inrecently visited cells; a MBSFN measurement result (e.g.,MeasResultMBSFN IE) and/or the like.

The wireless device 1601 may initiate a random access procedure, forexample, by sending (e.g., transmitting) one or more random accesspreambles to a base station (e.g., the base station DU 1602 and/or thebase station CU 1603) via one or more cells. The wireless device 1601may send (e.g., transmit) the one or more random access preambles, forexample, before sending (e.g., transmitting) a first RRC message 1610-A.The random access procedure with the base station (e.g., the basestation DU 1602 and/or the base station CU 1603) may be successful. Arandom access report IE may indicate at least one of: a number ofpreambles sent (e.g., numberOfPreamblesSent IE) and/or a contentiondetection indication (e.g., contentionDetected IE). The number ofpreambles sent (e.g., transmitted) may indicate a number of preamblessent (e.g., transmitted) by the wireless device (e.g., a MAC entity ofthe wireless device 1601) for the random access procedure with the basestation (e.g., a last successfully completed random access procedure).The contention detection indication may indicate whether contentionresolution was not successful for at least one of the one or more randomaccess preambles of the random access procedure with the base station(e.g., whether contention resolution was not successful for at least oneof transmitted preambles for a last successfully completed random accessprocedure). A contention detection indication may indicate a first value(e.g., “true” or 1), for example, if contention resolution was notsuccessful for at least one of transmitted preambles for a lastsuccessfully completed random access procedure, The contention detectionindication may indicate a second value (e.g., “false” or 0), forexample, if contention resolution was successful for all (or at leastone) of transmitted preambles for a last successfully completed randomaccess procedure.

The wireless device 1601 may attempt a connection establishment to oneor more cells and/or to a base station (e.g., the base station 1602 CUand/or the base station DU 1603). A connection establishment failurereport IE may comprise information of a failed connection establishmentattempt. The connection establishment failure report IE may comprise oneor more of: a failed cell identifier of a failed cell (e.g.,failedCellId IE) in which the wireless device 1601 attempted theconnection establishment and failed, location information (e.g.,locationInfo IE, ellipsoid based location information, GNSS basedlocation information, velocity information) in which the wireless devicefailed a connection establishment; measurement results (e.g., RSRPand/or RSRQ) of a failed cell (e.g. measResultFailedCell IE) from whichthe wireless device 1601 attempted the connection establishment andfailed, measurement result (e.g., RSRP and/or RSRQ) of neighbor cells(e.g., measResultNeighCells IE) of the failed cell, a number ofpreamble(s) sent (e.g., numberOfPreamblesSent IE) during the attempt ofthe connection establishment, a number of preamble(s) sent (e.g.,numberOfPreamblesSent IE) indicating a number of preambles sent by thewireless device (e.g., a MAC entity of the wireless device) for theattempt of the connection establishment, a contention detectionindication (e.g., contentionDetected IE, such as a “true” or “false”indication) indicating whether contention resolution was not successfulfor at least one of one or more random access preambles of the attemptof the connection establishment, a maximum transmission power reachedduring the attempt of the connection establishment for random accesspreamble transmission (e.g., maxTxPowerReached IE indicating whether ornot the maximum power level was used for the last transmitted preamble),a time duration after the failed connection establishment attempt (e.g.,timeSinceFailure IE indicating a time elapsed after a last HOinitialization until failure, wherein an actual value may be field valuemultiplied by 100 ms, e.g., value 1023 may indicate 102.3 seconds orlonger), and/or the like. A timeSinceFailure IE may indicate a time thatelapsed after a last connection establishment failure.

A power preference indication (e.g., a power preference indication IE)may indicate that the wireless device 1601 prefers a configuration forpower saving. The power preference indication may comprise an enumeratedvalue indicating, for example, normal and/or low power consumption. Abandwidth preference (e.g., a bandwidth preference IE) may indicatepreference of the wireless device for a bandwidth configuration and/orfor a maximum PDSCH and/or PUSCH bandwidth for uplink and/or downlink.The bandwidth preference IE may comprise enumerated values indicating,for example, mhz1dot4, mhz5, and/or mhz20.

A radio link monitoring (RLM) report (e.g., RLM IE) may indicate atleast one of RLM event information (e.g., rlm-Event IE) and/or an excessnumber of repetitions on an MPDCCH (e.g., excessRep-MPDCCH IE). The RLMevent information may indicate an RLM event. The RLM event may comprisean enumerated value indicating early-out-of-sync (e.g., if T314 expires)or early-in-sync (e.g., if T315 expires). The excess number ofrepetitions on MPDCCH may comprise an enumerated value, for example,indicating excessRep1 and/or excessRep2 that may be received from alower layer (e.g., if T315 expires).

A delay budget report (e.g., a delay budget report IE) may indicate apreferred adjustment to a connected mode discontinuous reception (DRX)and/or a coverage enhancement configuration. The delay budget report maycomprise, for example, a type 1 value and/or a type 2 value indicatingtiming delay budget information of the wireless device (e.g., −1280 ms,−160 ms, 0 ms, 80 ms, 1280 ms, −192 ms, −48 ms, 0 ms, 96 ms, 192 ms),and/or the like.

A logged measurement report (e.g., a logged measurement report IE) maycomprise at least one of time stamp information (e.g., absoluteTimeStampIE) for trace information such as logged measurement results (e.g.,which may indicate an absolute time for which logged measurementconfiguration logging is provided), trace reference information (e.g.,traceReference IE), trace recording session reference information (e.g.,traceRecordingSessionRef IE), trace identifier (e.g., tce-Id IE, tracecollection entity identifier), logged measurement information (e.g.,logMeasInfo IE), logged measurement information availability indication(e.g., logMeasAvailable IE) indicating whether or not logged measurementresult is available.

The logged measurement information may indicate at least one of locationinformation (e.g., locationInfo IE, ellipsoid based locationinformation, GNSS based location information, velocity information) forwhich the wireless device 1601 logged measurement information, timeinformation of logged data (e.g., relativeTimeStamp IE), serving cellidentifier (e.g., servCellIdentity IE) of a serving cell where thewireless device 1601 logged measurement information, measurement resultof the serving cell (e.g., measResultServCell IE indicating RSRP and/orRSRQ), measurement result of neighbor cells of the serving cell (e.g.,measResultNeighCells IE indicating RSRP and/or RSRQ), indicationparameter (e.g., inDeviceCoexDetected IE) indicating that measurementlogging is suspended due to IDC problem detection and/or whether or notin-device-coexistence was detected.

A mobility history report (e.g., mobility history report IE) mayindicate a visited cell list of the wireless device 1601. The mobilityhistory report may comprise one or more cell identifier(s) of one ormore cells that the wireless device 1601 visited. The mobility historyreport may indicate a time duration of stay in one or more cells (e.g.,16 most recently visited NR cells, E-UTRA cells, UTRA cells, and/orout-of-NR cells).

An MBSFN measurement result for one or more MBMS services that thewireless device 1601 receives may indicate at least one of MBSFN areainformation (e.g., mbsfn-Area IE comprising MBSFN area identifier (e.g.,mbsfn-Areald IE) and/or carrier information of MBSFN (e.g., carrierFreqIE)), measurement information of the MBSFN comprising an RSRP result(e.g., rsrpResultMBSFN IE) and/or RSRQ result (e.g., rsrqResultMBSFNIE), block error rate information of the MBSFN (e.g.,signallingBLER-Result IE indicating error rate of transport blocksassociated with the MBSFN and/or MBMS service), data block error rate ofa multicast channel (e.g., DataBLER-MCH-Result IE comprising mch-Indexand/or dataBLER-Result) indicating an error rate of a transport blockassociated with one or more multicast channels, and/or the like.

The base station CU 1603 may send (e.g., transmit, forward, etc.), tothe base station DU 1602, a first message 1611. The first message 1611may comprise wireless device information associated with the wirelessdevice 1601. The base station CU 1603 may send the first message 1611,for example, after or in response to receiving the first RRC message1610-A and/or 1610-B (and/or the first F1-C message) from the wirelessdevice 1601 (and/or from the base station DU 1602). The base station CU1603 may send (e.g., transmit, forward, etc.) the first message 1611 tothe base station DU 1602 via the F1 interface (e.g., the first message1611 may comprise a second F1-C message). The first message 1611 maycomprise, for example, a wireless device (e.g., UE) context setuprequest message, a wireless device (e.g., UE) context modificationrequest message, a wireless device (e.g., UE) context modificationconfirm message, a DL RRC message transfer message, and/or the like. Thefirst message 1611 may comprise a wireless device (e.g., UE) identifierof the wireless device 1601 (e.g., gNB-CU UE F1AP ID, gNB-DU UE F1AP ID,and/or the like). The first message 1611 may comprise the wirelessdevice (e.g., UE) information associated with the wireless device 1601.The first message 1611 may comprise a CU to DU RRC information IEcomprising one or more elements of the wireless device (e.g., UE)information.

The first message 1611 may comprise the wireless device (e.g., UE)information. The base station DU 1602 may determine at least one cellconfiguration parameter (e.g., one or more radio resource configurationparameters) of one or more cells of the base station DU 1602 for one ormore wireless devices (e.g., the wireless device 1601 and/or one or moreof wireless device 1604-A, 1604-B, and/or 1604-C, or any other wirelessdevice). The base station DU 1602 may determine the at least one cellconfiguration parameter, for example, after or in response to receivingthe first message 1611. The base station DU 1602 may determine the atleast one cell configuration parameter, for example, based on thewireless device information (e.g., that may be included in the firstmessage 1611). The one or more radio resource configuration parametersmay be for uplink (e.g., wireless device 1601 to base station DU 1602and/or to base station CU 1603), sidelink (e.g., wireless device1601-to-wireless device 1604-A, 1604-B, and/or 1604-C), and/or downlink(e.g., base station DU 1602 and/or base station CU 1603 to wirelessdevice 1601). The one or more cells may comprise a failed cell (e.g.,indicated by a connection establishment failure report) of the wirelessdevice 1601. The one or more radio resource configuration parameters maycomprise one or more of: a beam configuration parameter; a bandwidthpart (BWP) configuration parameter; a transmission power configurationparameter; a frequency configuration parameter; a beamformingconfiguration parameter; a physical control channel schedulingparameter; an antenna configuration parameter; a cell selection and/orreselection configuration parameter for one or more wireless devices(e.g., the wireless device 1601 and/or one or more of wireless device1604-A, 1604-B, and/or 1604-C, or any other wireless device); systeminformation; an interference control parameter; an MBSFN configurationparameter, and/or the like.

The base station DU 1602 may determine one or more of the at least onecell configuration parameter for the wireless device 1601, for example,based on preference information of the wireless device 1601. Preferenceinformation of the wireless device 1601 may be based on, for example,one or more of: a power preference indication (e.g., power preferenceindication IE), bandwidth preference (e.g., bandwidth preference IE),and/or a delay budget report (e.g., delay budget report IE). The basestation DU 1602 may configure one or more parameters to satisfy one ormore conditions of the preference information of the wireless device1601.

The base station DU 1602 may configure one or more MBSFN configurationparameters, for example, based on the MBSFN measurement result. The basestation DU 1602 may increase transmission power for the one or moreMBSFNs, for example, if RSRP and/or RSRQ of the wireless device 1601 forone or more MBSFNs is low (e.g., below a threshold value). The basestation DU 1602 may increase transmission power for the one or moreMBSFNs, for example, if BLER of one or more MBSFNs (e.g., one or moreMBMS services) is high (e.g., above a threshold value).

The at least one beam configuration parameters may be for one or morewireless devices (e.g., the wireless device 1601 and/or one or more ofwireless device 1604-A, 1604-B, and/or 1604-C, or any other wirelessdevice). The at least one beam configuration parameters may comprise oneor more parameters indicating at least one of: a plurality of beamindexes of a plurality of beams; a plurality of SSB beam configurations;a plurality of CSI-RS beam configurations; a plurality of beamdirections of a plurality of beams; a subcarrier spacing for a pluralityof beams; a cyclic prefix; a number of contiguous PRBs; an index in theset of one or more DL beams and/or one or more UL beams; a link betweena DL beam and/or an UL beam from a set of configured DL beams and/or ULbeams; a DCI detection to a PDSCH reception timing value; a PDSCHreception to a HARQ-ACK transmission timing value; a DCI detection to aPUSCH transmission timing value; an offset of a first PRB of a DLbandwidth or an UL bandwidth, respectively, relative to a first PRB of abandwidth; and/or the like.

The at least one beam configuration parameters may comprise one or moreparameters indicating at least one of CSI-RS beam indexes, SS beamindexes, BRACH resource configurations, BRACH preamble configurationparameters, beam based SRS transmission configuration information, beambased CSI-RS configuration parameters, beam based SS configurationparameters, beam failure recovery timer, number of random accesspreamble transmission repetitions, beam measurement configurationparameters, beam failure detection RS resource configuration information(e.g., Beam-Failure-Detection-RS-ResourceConfig), candidate beam RS list(e.g., Candidate-Beam-RS-List) for radio link quality measurements onthe serving cell, beam failure candidate beam received power threshold(e.g., Beam-failure-candidate-beam-threshold), control resource set(CORESET) information for beam failure recovery response (e.g.,Beam-failure-Recovery-Response-CORESET), RACH resource for beam failurerecovery procedure (e.g., Beam-failure-recovery-request-RACH-Resource),time window information for beam failure recovery request (e.g.,Beam-failure-recovery-request-window), TCI-StatesPDCCH, and/or the like.

The base station DU 1602 may reconfigure uplink and/or downlinktransmission power for the first beam for one or more wireless devices(the wireless device 1601 and/or one or more of wireless device 1604-A,1604-B, and/or 1604-C, or any other wireless device), for example, if awireless device experiences a failure during a time that a first beam ofa plurality of beams of a cell is used.

The base station DU 1602 may determine and/or indicate that one or morewireless devices are to use a second beam if measurement results of theone or more wireless device are similar to measurement results of thewireless device at a failure, for example, if a channel quality (e.g.,RSRP and/or RSRQ) of the second beam of a plurality of beams of a cellis good at a time that a wireless device experiences a failure and atime that a first beam is used.

At least one BWP configuration parameter may be for one or more wirelessdevices (e.g., the wireless device 1601 and/or one or more of wirelessdevice 1604-A, 1604-B, and/or 1604-C, or any other wireless device). Theat least one BWP configuration parameter may comprise one or moreparameters indicating at least one of: a plurality of BWP indexes of aplurality of BWPs; a plurality of BWP bandwidths of a plurality of BWPs;a default BWP index of a default BWP of the plurality of BWPs; a BWPinactivity timer; an initial BWP index of an initial BWP (e.g., initialactive BWP) of a plurality of BWPs; a subcarrier spacing for a pluralityof BWPs; a cyclic prefix; a number of contiguous PRBs; an index in theset of one or more DL BWPs and/or one or more UL BWPs; a link between aDL BWP and an UL BWP from a set of configured DL BWPs and UL BWPs; a DCIdetection to a PDSCH reception timing value; a PDSCH reception to aHARQ-ACK transmission timing value; a DCI detection to a PUSCHtransmission timing value; an offset of a first PRB of a DL bandwidth oran UL bandwidth, respectively, relative to a first PRB of a bandwidth;and/or the like.

The base station DU 1602 may not configure the first BWP as a defaultBWP (and/or as an initial BWP) for one or more wireless devices (e.g.,the wireless device 1601 and/or one or more of wireless device 1604-A,1604-B, and/or 1604-C, or any other wireless device), for example, if awireless device experiences a failure at a time that a first BWP of aplurality of BWPs of a cell is an active BWP. The base station DU 1602may configure the second BWP as a default BWP (and/or as an initial BWP)for one or more wireless devices (g., the wireless device 1601 and/orone or more of wireless device 1604-A, 1604-B, and/or 1604-C, or anyother wireless device), for example, if a channel quality (e.g., RSRPand/or RSRQ) of a second BWP of a plurality of BWPs of a cell is good(e.g., better than a channel quality of an active BWP) at a time that awireless device experiences a failure and a time that a first BWP of theplurality of BWPs is an active BWP.

At least one transmission power configuration parameter may comprise oneor more of: a maximum downlink/uplink cell transmission power, aphysical downlink control channel (PDCCH) transmission power, a powercontrol parameter for uplink and/or downlink, a TPC configurationparameter, an SRS configuration parameter, and/or the like for one ormore wireless devices (e.g., the wireless device 1601 and/or one or moreof wireless device 1604-A, 1604-B, and/or 1604-C, or any other wirelessdevice) and/or for the base station DU 1602. The base station DU 1602may increase a transmission power of the PDCCH, for example, if the basestation DU 1602 determines that a failure occurred because of a lowtransmission power of a PDCCH (e.g., based on measurement results of thewireless device information). The base station DU 1602 may reschedulethe PDCCH to be located at other subframes, for example, if a failureoccurred because of large interferences on a PDCCH.

The base station DU 1602 may increase an uplink and/or downlink powerlevel (e.g., 0.1 dB increase) for one or more wireless devices (e.g.,wireless device(s) served in the first cell) at a time that the one ormore wireless devices use the first beam, for example, if a wirelessdevice experiences a failure during a time that a first beam is used.The base station DU 1602 may not configure the first beam for a randomaccess preamble transmission of one or more wireless devices, forexample, if a cause of a failure of a wireless device is a random accessproblem and the wireless device experiences the failure at a time that afirst beam is used. The base station DU 1602 may increase an uplinkpower level for one or more wireless devices at a time that one or morewireless devices use a first beam, for example, if a cause of thefailure of a wireless device is an RLC maximum number of retransmissions(e.g., uplink transmission problem and/or a number of RLCretransmissions is above a threshold value) and the wireless deviceexperiences a failure at a time that a first beam is used.

At least one frequency configuration parameter may comprise one or moreof: a carrier frequency, a bandwidth, a bandwidth part configurationparameter, and/or the like. The base station DU 1602 may change anoperation frequency to other frequency, for example, if a cell of thebase station DU 1602 experiences large interferences (e.g., interferenceabove a threshold value) such as from neighboring cells or othertechnologies. The base station DU 1602 determine and/or indicate thatone or more wireless devices is to use a beam other than a certain beamif measurement results of the one or more wireless devices are similarto measurement results of the wireless device at a failure, for example,if the certain beam of a served cell of the base station DU 1602experiences large interferences (e.g., interference above a thresholdvalue) such as from neighboring cells or other technologies.

At least one beamforming configuration parameter may comprise one ormore of: a beamforming direction configuration parameter, a beamsweeping configuration parameter, a synchronization signal (SS) and/or areference signal (e.g., CSI-RS) configuration parameter, a beam recoveryrelated parameter, a BRACH parameter, a preamble configuration parameterfor beam recovery, a random access configuration parameter of one ormore beams, and/or the like. The base station DU 1602 may reschedulerandom access resources and/or BRACH resources, and/or may reconfigurepreambles to reduce random access contentions, for example, if thefailure occurred because of a random access failure and/or because of afailure of a beam recovery procedure (e.g., out-of-sync).

At least one physical control channel scheduling parameter may compriseone or more of: a subframe pattern configuration parameter, ameasurement subframe pattern configuration parameter, a transmissiontype parameter indicating a localized transmission and/or distributedtransmission, a resource block assignment configuration parameter, aCSI-RS configuration parameter, and/or the like. At least one antennaconfiguration parameter may comprise one or more of: a default antennaconfiguration parameter, an antenna port configuration parameter, anumber of CRS antenna port parameter, and/or the like. At least one cellselection and/or reselection configuration parameter for one or morewireless devices may comprise one or more of: a power and/or timethreshold parameter for cell selection and/or reselection of at leastone wireless device (e.g., in communication with the base station), acell priority configuration parameter for cell selection and/orreselection, and/or the like. The base station DU 1602 may increase avalue of one or more power and/or time threshold parameters, forexample, if a failure occurred because of a random access failure of awireless device. Increasing values of one or more power and/or timethreshold parameters may assist a wireless device in avoiding a failedcell (e.g., if the wireless device does not satisfy increased one ormore thresholds).

The base station DU 1602 may reconfigure one or more IEs of systeminformation. The system information may comprise one or more of systeminformation block type 1 to 21, for example, based on the wirelessdevice information. At least one interference control parameter maycomprise one or more almost blank subframe configuration parameters, oneor more CoMP interference management related parameters, and/or thelike. The base station DU 1602 may schedule resource blocks for aneighboring cell and/or a failed cell not to use the resource blockssimultaneously, for example, if a failure occurred because ofinterference from the neighboring cell of the failed cell.

The base station DU 1602 and/or the base station CU 1603 may send (e.g.,transmit, forward, etc.) at least one system information blockcomprising one or more radio resource configuration parameters. The atleast one system information blocks may comprise at least one of thesystem information block type 1 to 21. The base station DU 1602 and/orthe base station CU 1603 may send (e.g., transmit, forward, etc.) atleast one cell configuration parameter for one or more wireless devices(e.g., via MAC CE, DCI, and/or an RRC message). The one or more wirelessdevices may comprise the wireless device 1601. The base station DU 1602may send (e.g., transmit, forward, etc.) a second message 1612 (e.g., atleast one system information blocks comprising one or more radioresource configuration parameters) to the base station CU 1603. Thesecond message 1612 may comprise configuration parameters (e.g., one ormore radio resource configuration parameters). The base station CU 1603may send (e.g., transmit, forward, etc.), to the base station DU 1602, asecond RRC message 1613-A. The second RRC message 1613-A may comprisethe configuration parameters. The configuration parameters may be forthe wireless device 1601. The base station DU 1602 may send (e.g.,transmit, forward, etc.), to the wireless device 1601, a second RRCmessage 1613-B. The second RRC message 1613-B may comprise at least someof the same information as the second RRC message 1613-A. The second RRCmessage 1613-B may comprise the configuration parameters (e.g.,configuration parameters for the wireless device 1601).

The base station CU 1603 may send (e.g., transmit, forward, etc.), tothe base station DU 1602, a third message 1614-A. Additionally oralternatively, the base station CU 1603 may send (e.g., transmit,forward, etc.), to at least one of wireless devices 1601, 1604-A,1604-B, 1604-C and/or any other wireless device, the third message1614-A. The third message 1614-A may comprise configuration parametersfor at least one of wireless devices 1604-A, 1604-B, and/or 1604-C(e.g., or any other wireless device such as the wireless device 1601).The configuration parameters may comprise one or more radio resourceconfiguration parameters. The base station DU 1602 may determine, basedon the configuration parameters in the third message, to which of aplurality of wireless devices (e.g., wireless devices 1601, 1604-A,1604-B, and/or 1604-C, or any other wireless device) the base station DU1602 should send the third message. The base station DU 1602 may send(e.g., transmit, forward, etc.), to the at least one of wireless devices1604-A, 1604-B, and/or 1604-C (e.g., or any other wireless device suchas the wireless device 1601), a third message 1614-B. The base stationDU 1602 may send (e.g., transmit, forward, etc.) the third message1614-B based on the determining to which of the plurality of wirelessdevices to send the third message 1614-B. The third message 1614-B maycomprise at least some of the same information as the third message1614-A. The third message 1614-B may comprise the configurationparameters for at least one of wireless devices 1604-A, 1604-B, and/or1604-C (e.g., or any other wireless device such as the wireless device1601).

The first message (e.g., 1610-A and/or 1610-B) may comprise the wirelessdevice (e.g., UE) information and/or one or more second radio resourceconfiguration parameters, for example, that may be determined by thebase station CU 1603 for the wireless device 1601 and/or one or morewireless devices 1604-A, 1604-B, and/or 1604-C. The base station CU 1603may determine the one or more second radio resource configurationparameters based on the wireless device (e.g., UE) information receivedfrom the wireless device 1601 (and/or from the base station DU 1602).The one or more second radio resource configuration parameters may befor an uplink and/or downlink transmission and/or for a sidelink (e.g.,wireless device-to-wireless device) transmission.

The one or more second radio resource configuration parameters maycomprise one or more of: a beam configuration parameter; a bandwidthpart (BWP) configuration parameter; a transmission power configurationparameter; a frequency configuration parameter; a beamformingconfiguration parameter; a physical control channel schedulingparameter; an antenna configuration parameter; a cell selection and/orreselection configuration parameter for one or more wireless devices(e.g., 1601, 1604-A, 1604-B, and/or 1604-C); system information; aninterference control parameter; an MBSFN configuration parameter, and/orthe like.

The base station DU 1602 may determine one or more radio resourceconfiguration parameters. The one or more radio resource configurationparameters may comprise, for example, one or more of: a beamconfiguration parameter, a bandwidth part (BWP) configuration parameter,a transmission power configuration parameter, a frequency configurationparameter, a beamforming configuration parameter, a physical controlchannel scheduling parameter, an antenna configuration parameter, a cellselection and/or reselection configuration parameter for one or morewireless devices, system information, an interference control parameter,an MBSFN configuration parameter, and/or the like. The base station DU1602 may determine the one or more radio resource configurationparameters, for example, based on the one or more second radio resourceconfiguration parameters and/or the wireless device information. Thebase station DU 1602 may configure one or more radio resourceconfiguration parameters as may be indicated in the one or more secondradio resource configuration parameters. The base station DU 1602 mayconfigure one or more radio resource configuration parameters modifiedfrom the one or more second radio resource configuration parameters(e.g., based on the wireless device information). The base station DU1602 may send (e.g., transmit, forward, etc.), to the base station CU1603, one or more radio resource configuration parameters modified fromthe one or more second radio resource configuration parameters, forexample, if the base station DU 1602 updates (e.g., modifies) the one ormore second radio resource configuration parameters.

After or in response to determining the one or more radio resourceconfiguration parameters based on the wireless device information,and/or after or in response to determining (e.g., configuring) the oneor more radio resource configuration parameters based on the one or moresecond radio resource configuration parameters and/or the wirelessdevice information, the base station DU 1602 may send the second message1612. The second message 1612 may comprise the one or more radioresource configuration parameters for the wireless device 1601 and/orone or more wireless devices (e.g., 1601, 1604-A, 1604-B, and/or1604-C). The second message 1612 may be a response message (e.g., inresponse to the first message 1611) indicating that the base station DU1602 configures cell and/or radio parameters based on the one or moresecond radio resource configuration parameters provided by the basestation CU 1603.

The base station CU 1603 may send (e.g., transmit, forward, etc.) thesecond RRC message 1613-A to the wireless device 1601 and/or one or morewireless devices (e.g., 1604-A, 1604-B, and/or 1604-C) via the basestation DU 1602. After or in response to receiving the second RRCmessage 1613-A, the base station DU 1602 may send (e.g., transmit,forward, etc.) the second RRC message 1613-B to the wireless device 1601and/or the one or more wireless devices (e.g., 1604-A, 1604-B, and/or1604-C). The base station CU 1603 may send the second RRC message 1613-Avia a second F1-C message (e.g., F1 control plane message). The secondRRC message 1613-A and/or 1613-B may comprise one or more of: a DL RRCmessage transfer message, a wireless device (e.g., UE) contextmodification request message, a wireless device (e.g., UE) contextmodification confirm message, a wireless device (e.g., UE) context setuprequest message, and/or the like. The second F1-C message may comprisean RRC-Container IE comprising the second RRC message 1613-A and/or16-13-B. In an example, the second RRC message 1613-A and/or 16-13-B maycomprise a wireless device (e.g., UE) identifier of the wireless device(e.g., gNB-CU UE F1 AP ID, gNB-DU UE F1 AP ID, old gNB-DU UE F1 AP ID,and/or the like), a signaling radio bearer identifier associated withthe second RRC message (e.g., SRB ID, which may comprise an integervalue from 0 to 3, e.g., SRB1), and/or the like.

The base station DU 1602 may send (e.g., transmit, forward, etc.) thesecond RRC message 1613-B via a signaling radio bearer 1 (e.g., SRB1).The base station DU 1602 may not interpret (and/or may not decode) thesecond RRC message 1613-A. The second RRC message 1613-A and/or 16-13-Bmay comprise an RRC connection reconfiguration message (e.g.,RRCConnectionReconfiguration message); an RRC connection setup, resume,and/or reestablishment message; and/or the like. The base station CU1603 may send (e.g., transmit, forward, etc.) the second RRC message1613-A via the F1 interface configured between the base station DU 1602and the base station CU 1603.

The base station CU 1603 may send (e.g., transmit, forward, etc.) atleast one system information block. The at least one system informationblock may comprise the one or more radio resource configurationparameters. The base station CU 1603 may send (e.g., transmit, forward,etc.), to the wireless device 1601, the at least one system informationblock via the base station DU 1602. The at least one system informationblock may comprise at least one of the system information block type 1to 21. The base station DU 1602 and/or the base station CU 1603 may send(e.g., transmit, forward, etc.) at least one cell configurationparameter to one or more wireless devices (e.g., 1601, 1604-A, 1604-B,and/or 1604-C), for example, via MAC CE, DCI, and/or an RRC message. Theone or more wireless devices may comprise the wireless device 1601. Thewireless device 1601 may use one or more radio resource configurationparameters indicated via the second RRC message 1613-B to send (e.g.,transmit, forward, etc.) transport blocks via an uplink and/or asidelink. The wireless device 1601 may use one or more resourceconfiguration parameters indicated via the second RRC message 1613-B toreceive transport blocks via a downlink. The base station DU 1602 maysend (e.g., transmit, forward, etc.), to the wireless device 1601 via aPDCCH (e.g., DCI) and/or via a MAC CE, an activation (and/ordeactivation) indication to activate (and/or deactivate) one or moreradio resources indicated via the second RRC message.

The base station CU 1693 may send (e.g., transmit, forward, etc.), tothe wireless device 1601 via an RRC message (e.g., the second RRCmessage and/or an additional RRC message), an activation and/ordeactivation indication to activate and/or deactivate the one or moreradio resources and/or the one or more radio configurations indicatedvia the second RRC message. The second RRC message may comprise anactivation indication for the one or more radio resources and/or the oneor more radio configurations. The wireless device 1601 may start anuplink transmission via the one or more radio resources, and/or use theone or more radio configurations at any moment and/or in a certaintiming (e.g., which may be configured by an RRC signaling orpre-defined) after the configuration is completed, for example, if theL1 activation (e.g., DCI) is not configured (e.g., the second RRCmessage 1613-A and/or 1613-B comprises the activation indication).

FIG. 17 shows an example data flow for messaging associated withwireless device information. At step 1705, a wireless device 1701 maysend, to a base station DU 1702, a first RRC message. The wirelessdevice 1701 may send the first RRC message to the base station CU 1703via the base station DU 1702. The base station DU 1702 may receive, fromthe wireless device 1701, the RRC message. The first RRC message maycomprise wireless device (e.g., user equipment (UE)) information of thewireless device. The wireless device information may comprise one ormore of: random access report information (e.g., random access reportinformation element (IE)); a connection establishment failure indication(e.g., connection establishment failure report IE); a power preferenceindication (e.g., power preference indication IE) indicating thewireless device prefers a configuration for power saving; a bandwidthpreference (e.g., bandwidth preference IE); a radio link monitoring(RLM) indication (e.g., RLM report IE); a delay budget indication (e.g.,delay budget report IE) indicating a preferred adjustment to connectedmode discontinuous reception (DRX) or coverage enhancementconfiguration; a logged measurement indication (e.g., a loggedmeasurement report IE); a mobility history indication (e.g., a mobilityhistory report IE) indicating at least one time value of stay inrecently visited cells; and/or a MeasResultMBSFN IE. At step 1706, thebase station DU 1702 may send (e.g., transmit, forward, etc.), to thebase station CU 1703 which may receive, the first RRC message (e.g.,comprising the wireless device information). The base station DU 1702may send (e.g., transmit, forward, etc.), to the base station CU 1703via an F1 interface, the first RRC message (e.g., without interpretationby the base station DU 1702). At step 1707, the base station CU 1703 maysend (e.g., transmit, forward, etc.), to the base station DU 1702 whichmay receive, a first message comprising the wireless device information.At step 1702, the base station DU 1702 may determine one or more radioresource configuration parameters based on the wireless deviceinformation. At step 1709, the base station DU 1702 may send (e.g.,transmit, forward, etc.), to the base station CU 1703, a second messagecomprising configuration parameters (e.g., the one or more radioresource configuration parameters).

At step 1710, the base station CU 1703 may send (e.g., transmit,forward, etc.), to the base station DU 1702 which may receive, a secondRRC message comprising the configuration parameters (e.g., the one ormore radio resource configuration parameters). At step 1711, the basestation DU may send (e.g., transmit, forward, etc.), to the wirelessdevice 1701, the second RRC message (e.g., without interpretation by thebase station DU 1702). At step 1712, the base station CU 1703 may send(e.g., transmit, forward, etc.), to the base station DU 1702, a thirdmessage. The third message may comprise configuration parameters (e.g.,one or more second radio resource configuration parameters) for one ormore wireless devices 1704. At step 1713, the base station DU 1702 maysend (e.g., transmit, forward, etc.), to the one or more wirelessdevices 1704, the third message (e.g., comprising the configurationparameters such as one or more second radio resource configurationparameters).

A random access report may comprise one or more of: a first number ofpreambles sent IE indicating a first number of preambles sent during arandom access process, and/or a first contention detected IE indicatingcontention was detected for at least one of transmitted preambles duringthe random access process. A logged measurement report IE may compriseone or more of: an absolute time stamp IE indicating an absolute time atwhich a logged measurement configuration logging is provided from a basestation; a trance reference IE; and/or the like. A connectionestablishment failure report IE may comprise at least one of a failedcell identifier of a failed cell, a location information IE, a failedcell measurement result IE, a neighbor cell measurement result IE, asecond number of preambles sent IE indicating a second number ofpreambles, a second contention detected IE, a maximum transmission powerreached IE, and/or a time since failure IE.

A mobility history report may comprise a visited cell information listcomprising at least one of at least one visited cell identifier of atleast one visited cell, at least one carrier frequency value of the atleast one visited cell, and/or at least one time spent IE indicating atleast one time spent in the at least one visited cell. The visited cellinformation list may comprise, for example, for at least one visitedcell: an identifier (e.g., an ID of the at least one visited cell), anindication of a frequency (e.g., a carrier frequency value of the atleast one visited cell), and/or a time (e.g., a time spent in the atleast one visited cell). The visited cell information list may comprise,for example, for each of a plurality of visited cells: an identifier(e.g., an ID of a visited cell), an indication of a frequency (e.g., acarrier frequency value of a visited cell), and/or a time (e.g., a timespent in a visited cell). The visited cell information list maycomprise, for example, at least a first list associated with a firstvisited cell and/or a second list associated with a second visited cell.The first list associated with the first visited cell may comprise, forexample, a first identifier (e.g., an ID of a first visited cell), afirst indication of a frequency (e.g., a carrier frequency value of thefirst visited cell), and/or a first time (e.g., a time spent in thefirst visited cell). The second list associated with the second visitedcell may comprise, for example, a second identifier (e.g., an ID of asecond visited cell), a second indication of a frequency (e.g., acarrier frequency value of the second visited cell), and/or a secondtime (e.g., a time spent in the second visited cell). The first visitedcell may be a most recently visited cell. The second visited cell may bea cell visited prior to the first visited cell. The visited cellinformation list may comprise any number of the above lists, each ofwhich may be associated with, for example, a visited cell.

A bandwidth preference (e.g., bandwidth preference IE) may comprise atleast one of a downlink preference IE indicating a preference for aconfiguration of a maximum physical downlink shared channel (PDSCH)bandwidth, an uplink preference IE indicating a preference for aconfiguration of a maximum physical uplink shared channel (PUSCH)bandwidth, and/or a sidelink preference IE indicating a preference for aconfiguration of a maximum physical sidelink channel bandwidth. An RLMreport (e.g., RLM report IE) may comprise at least one of an RLM eventIE indicating one of early-out-of-sync or early-in-sync, and/or anexcess repetition machine type communication physical downlink controlchannel (MPDCCH) IE indicating an excess number of repetitions onMPDCCH. A delay budget report (e.g., delay budget report IE) maycomprise at least one of a type 1 IE and/or a type 2 IE.

Any one or more methods described herein with respect to a base stationCU (e.g., by the base station CU 1703 and or by the base station CU1603) may be performed by any combination of one or more of: a basestation DU (e.g., a second base station DU), a base station CU, and/or aneighboring base station. Any one or more methods described herein withrespect to a base station DU (e.g., by the base station DU 1702 and orby the base station DU 1602) may be performed by any combination of oneor more of: a base station DU (e.g., a second base station DU), a basestation CU, and/or a neighboring base station. Multiple base stations(e.g., multiple base station DUs) may be used to perform one or moremethods described herein, for example, for dual-connectivity and/or forcarrier aggregation.

FIG. 18 shows an example data flow for messaging associated withwireless device information. A wireless device 1801 may communicate witha base station central unit (CU) 1803 via one or more base station DUs(e.g., 1802-A and/or 1802-B) and/or via a second base station (e.g.,1802-B). The base station 1802-B may comprise a base station DU and/or asecond base station. A first base station may comprise the base stationCU 1803 and one or more base station DUs (e.g., 1802-A and/or 1802-B). Asecond base station may comprise the base station 1802-B. The messagingshown in FIG. 18 may comprise some or all of the messaging describedabove regarding FIG. 17, unless indicated otherwise herein. Steps1805-1813 may correspond to steps 1705-1713, respectively, describedabove regarding FIG. 17, except that one or more steps by the basestation DU 1702 may be performed by any combination of the base stationDU 1802-A and/or the base station 1802-B.

At step 1808, the base station 1802-B may determine, based on thewireless device information, configuration parameters for the wirelessdevice 1801. The base station 1802-B may determine, based on thewireless device information, configuration parameters (e.g., radioresource configuration parameters) for the wireless device 1801. At step1809, the base station 1802-B may send, to the base station CU 1803, asecond message. The second message may comprise configurationparameters. The configuration parameters may comprise radio resourceconfiguration parameters for the wireless device 1801. The configurationparameters may comprise, for example, a configured grant for thewireless device 1801. At step 1810, the base station CU 1803 may send,to the base station DU 1802-A, a second RRC message. The second RRCmessage may comprise the configuration parameters for the wirelessdevice 1801. At step 1811, the base station DU 1802-A may send (e.g.,transmit, forward, etc.), to the wireless device 1801, the second RRCmessage comprising the configuration parameters.

FIG. 19 shows examples of communications between a wireless device and abase station. Communications to and from devices in FIG. 19 may compriseany of the communications described above regarding FIGS. 16-18. Awireless device 1901-A may communicate with a base station CU 1903-A viaa base station DU 1902-A. A wireless device 1901-B may communicate witha base station CU 1903-B via multiple base station DUs 1902-B1 and1902-B2. The wireless device 1901-C may communicate with a base stationCU 1903-C via a base station DU 1902-C and a secondary base station1904. The base station CUs 1903-A, 1903-B, and 1903-C may communicatewith the base station DUs 1902-A, 1902-B, and 1902-C, respectively, viaan F1 interface. The base station CU 1903-C may communicate with thesecondary base station 1904 via an Xn interface.

FIG. 20 shows an example of configuring a wireless device withparameters based on wireless device information (e.g., power preferenceindication that the wireless device prefers a configuration for powersaving). At step 2001, a wireless device may establish and/orre-establish a connection with a base station, such as a base station CUand/or a base station DU. At step 2002, the wireless device maydetermine one or more parameters comprising at least wireless deviceinformation. The wireless device information may comprise one or moreof: a random access report (e.g., IE), a connection establishmentfailure report (e.g., IE), a power preference indication (e.g., IE)indicating that the wireless device prefers a configuration for powersaving, a bandwidth preference, an RLM report (e.g., IE), a delay budgetreport (e.g., IE) indicating a preferred adjustment to a connected modeDRX and/or coverage enhancement configuration, a logged measure report(e.g., IE), a mobility history report (e.g., IE) indicating at least onetime value of stay in recently visited cells; and/or a MBSFN measurementresult (e.g., IE). At step 2004, the wireless device may receive (and/ordetermine whether it receives), from the base station CU (e.g., via thebase station DU), at least one RRC message. The at least one RRC messagemay comprise configuration parameters (e.g., radio configurationparameters) for a cell of the base station DU determined based on thewireless device information. If the wireless device receives (and/ordetermines that it receives) the at least one RRC message, the wirelessdevice may send (e.g., transmit), to the base station CU (e.g., via thebase station DU), at least one RRC response message for the at least oneRRC message. At step 2006, the wireless device may send transport blocksto the base station DU and/or receive transport blocks from the basestation DU. The wireless device may send and/or receive the transportblocks based on the configuration parameters (e.g., radio configurationparameters).

FIG. 21 shows an example of providing configuration parameters that maybe performed by a base station distributed unit (DU). At step 2101, abase station DU may configure wireless device (e.g., UE) contexts for awireless device and/or establish (and/or re-establish) a connection withthe wireless device. The base station DU may configure the wirelessdevice contexts based on communicating with a base station CU. At step2102, the base station DU may receive, from the wireless device,wireless device (e.g., UE) information. The wireless device informationmay comprise, for example, a power preference indication that thewireless device prefers a configuration for power saving. The wirelessdevice information may comprise at least one of: a random access report(e.g., IE), a connection establishment failure report (e.g., IE), apower preference indication (e.g., IE) indicating that the wirelessdevice prefers a configuration for power saving, a bandwidth preference(e.g., IE), an RLM report (e.g., IE), a delay budget report (e.g., IE)indicating a preferred adjustment to a connection mode DRX and/or acoverage enhancement configuration, a logged measurement report (e.g.,IE), a mobility history report (e.g., IE) indicating at least one timevalue of stay in recently visited cells, and/or an MBSFN measurementresult (e.g., IE). At step 2103, the base station DU may send (e.g.,transmit, forward, etc.), to the base station CU, the wireless deviceinformation. At step 2104, the base station DU may receive, from thebase station CU, a message. The message may comprise one or moreelements of the wireless device information.

At step 2105, the base station DU may determine whether the base stationDU should (e.g., needs to) update radio configurations based on the oneor more elements of the wireless device information. If the base stationDU determines that it should update radio configurations, at step 2106,the base station DU may determine one or more radio configurationparameters based on the wireless device information. At step 2107, thebase station DU may send (e.g., transmit, forward, etc.), to the basestation CU, the one or more radio configuration parameters. At step2108, the base station DU may receive, from the base station CU, atleast one RRC message comprising the one or more radio configurationparameters. At step 2109, the base station DU may send (e.g., transmit,forward, etc.), to the wireless device and/or to one or more otherwireless devices, the at least one RRC message comprising the one ormore configuration parameters.

At step 2110, the base station DU may receive (and/or determine whetherit receives), from the wireless device and/or from the one or more otherwireless devices, at least one RRC response message indicatingconfiguration of the radio configuration parameters. If the base stationDU receives the at least one RRC response message, at step 2111, thebase station DU may send (e.g., transmit, forward, etc.), to the basestation CU, the at least one RRC response message. At step 2112, thebase station DU may receive, from the wireless device based on the radioconfiguration parameters, one or more transport blocks; and/or the basestation DU may send (e.g., transmit, forward), to the base station CUbased on the radio configuration parameters, the one or more transportblocks and/or data of the one or more transport blocks.

FIG. 22 shows an example of providing configuration parameters that maybe performed by a base station central unit (CU). At step 2201, a basestation CU may establish and/or re-establish a connection with awireless device. At step 2202, the base station CU may receive, from thewireless device (e.g., via a base station DU), wireless device (e.g.,UE) information. The wireless device information may comprise, forexample, a power preference indication that the wireless device prefersa configuration for power saving. The wireless device information maycomprise at least one of: a random access report (e.g., IE), aconnection establishment failure report (e.g., IE), a power preferenceindication (e.g., IE) indicating that the wireless device prefers aconfiguration for power saving, a bandwidth preference (e.g., IE), anRLM report (e.g., IE), a delay budget report (e.g., IE) indicating apreferred adjustment to a connection mode DRX and/or a coverageenhancement configuration, a logged measurement report (e.g., IE), amobility history report (e.g., IE) indicating at least one time value ofstay in recently visited cells, and/or an MBSFN measurement result(e.g., IE). The traffic pattern information may indicate at least oneof: a periodicity (e.g., a data arrival periodicity), an offset (e.g., adata arrival timing offset), and/or a size (e.g., a message size, a datasize, etc.). At step 2203, the base station CU may determine whether thewireless device information comprises RRC layer related information(e.g., mobility preference, cell preference, moving speed, movingpattern, mobility history, and/or the like). If the base stationdetermines that the wireless device information comprises RRC layerrelation information, at step 2204, the base station CU may configure,based on the wireless device information, RRC parameters. At step 2205,the base station CU may configure (e.g., add, modify, and/or release)secondary cells based on the wireless device information. The basestation CU may configure the secondary cells, for example, if the basestation CU determines that the wireless device information does notcomprise RRC layer related information (e.g., at step 2203) and/or ifthe base station CU configures RRC parameters based on the wirelessdevice information (e.g., at step 2204). At step 2206, the base stationCU may send (e.g., transmit), to a base station DU, a message. Themessage may comprise one or more elements of the wireless deviceinformation.

At step 2207, the base station CU may receive (and/or determine whetherit receives), from the base station DU, one or more radio configurationparameters (e.g., that may be determined based on the wireless deviceinformation). The one or more radio configuration parameters may bedetermined, for example, based on the wireless device information. Atstep 2208, the base station CU may send (e.g., transmit), to thewireless device (e.g., via the base station DU) and/or to one or moreother wireless devices (e.g., via the base station DU), at least one RRCmessage comprising the one or more radio configuration parameters. Atstep 2209, the base station CU may receive, from the wireless device(e.g., via the base station DU) and/or from the one or more otherwireless devices (e.g., via the base station DU), at least one RRCresponse message. The at least one RRC response message may indicateconfiguration of the one or more radio configuration parameters.

A wireless device may determine wireless device information comprisingan indication of a power configuration for the wireless device. Thewireless device may send, to a base station distributed unit (DU) thatmay receive, a first radio resource control (RRC) message comprisingwireless device information. The wireless device information maycomprise an indication of a power configuration for the wireless device.The indication of the power configuration for the wireless device maycomprise a power preference indication indicating that the wirelessdevice prefers a configuration for power saving. The indication of thepower configuration for the wireless device may comprise one or more ofa random access report (e.g., random access report information element(IE)), a connection establishment failure report (e.g., a connectionestablishment failure report IE), a power preference indication (e.g.,power preference indication IE) indicating that the wireless deviceprefers a power configuration for power saving, a bandwidth preference(e.g., a bandwidth preference IE), a radio link monitoring (RLM) report(e.g., an RLM report IE), a delay budget report (e.g., a delay budgetreport IE) indicating a preferred adjustment to connection modediscontinuous reception (DRX) or coverage enhancement configuration, alogged measurement report (e.g., a logged measurement report IE), amobility history report (e.g., a mobility history report IE) which mayindicate at least one time value of stay in recently visited cells, ameasurement report, and/or a measurement result (e.g., a MeasResultMBSFNIE). The wireless device information may comprise at least one of: afirst number of preambles sent IE indicating a first number of preamblessent during a random access process; or a first contention detected IEindicating contention was detected for at least one of transmittedpreambles during the random access process. The wireless deviceinformation may comprise at least one of: an absolute time stamp IEindicating an absolute time that a logged measurement configurationlogging is provided from a base station; or a trance reference IE. Thewireless device information may comprise at least one of: a failed cellidentifier of a failed cell, a location information IE, a failed cellmeasurement result IE, a second number of preambles sent IE indicating asecond number of preambles, a second contention detected IE, a maximumtransmission power reached IE, and/or a time since failure IE. Thewireless device information may comprise a visited cell information listcomprising at least one of: a visited cell identifier of at least onevisited cell, or a time spent IE indicating that at least one time spentin the at least one visited cell. The wireless device information maycomprise at least one of: a downlink preference IE indicating apreference for a configuration of a maximum physical downlink sharedchannel (PDSCH) bandwidth, an uplink IE indicating a preference for aconfiguration of a maximum physical uplink shared channel (PUSCH)bandwidth, and/or a sidelink (e.g., wireless device-to-wireless device)preference IE indicating a preference for a configuration of a maximumphysical sidelink channel. The wireless device information may compriseat least one of: an RLM event (e.g., an RLM event IE) indicating anearly-out-of-sync and/or an earlier-in-sync, and/or an excess repetitionmachine type communication physical downlink control channel (MPDCCH) IEindicating an excess repetition machine type communications on anMPDCCH. The wireless device information may comprise a delay budgetreport IE comprising at least one of: a type 1 IE, and/or a type 2 IE.The base station DU may send, to a base station central unit (CU) thatmay receive, the first RRC message comprising the wireless deviceinformation. The wireless device information may comprise overheatingassistance information. The overheating assistance information mayindicate that the wireless device is overheated and/or in a high loadstatus. The overheating assistance information may provide recommendedconfigurations to resolve overheating issue and/or overload status. Theoverheating assistance information may comprise at least one of: areduced component carrier field, a reduced bandwidth field, a reducedMIMO field, and/or the like. The reduced component carrier field (e.g.,reducedCCsDL, reducedCCsUL, etc.) may indicate that the wireless deviceneeds to reduce the number of component carriers (e.g., secondary cells,serving cells, etc.) for uplink and/or downlink. The reduced componentcarrier field may indicate that the wireless device needs to use a lessthan or equal number of component carriers (e.g., secondary cells,serving cells, etc.) than a value indicated for uplink and/or downlink.The reduced bandwidth field (e.g., reducedBW-FR1-DL, reducedBW-FR1-UL,reducedBW-FR2-DL, reducedBW-FR2-UL, etc.) may indicate that the wirelessdevice needs to reduce the number of aggregated bandwidth for uplinkand/or downlink. The reduced bandwidth field may indicate that thewireless device needs to use a less than or equal number of aggregatedbandwidth than a value indicated for uplink and/or downlink. The reducedMIMO field (e.g., reducedMIMO-LayersFR1-DL, reducedMIMO-LayersFR1-UL,reducedMlMO-LayersFR2-DL, reducedMlMO-LayersFR2-UL, etc.) may indicatethat the wireless device needs to reduce the number of MIMO layers foruplink and/or downlink. The reduced MIMO field may indicate that thewireless device needs to employ a smaller or equal number of MIMO layersthan/to a value indicated for uplink and/or downlink.

The base station DU may send the first RRC message by forwarding (e.g.,without interpreting, without decoding, etc.), to the base station CUvia an F1 interface, the first RRC message from the wireless device(e.g., without interpretation and/or decoding of the first RRC message).The base station CU may receive the first RRC message. The base stationCU may determine that the wireless device information is associated witha wireless device that is associated with the base station DU. The basestation CU may send to the base station DU that may receive, a firstmessage comprising the wireless device information. The base station DUmay determine, based on the wireless device information, at least onepower configuration parameter. The base station DU may send, to the basestation CU that may receive, a second message comprising the at leastone power configuration parameter. The base station CU may send, to thewireless device (which may receive) via the base station DU (which mayreceive and/or forward), a second RRC message comprising a powerconfiguration parameter (e.g., the at least one power configurationparameter and/or one or more other power configuration parameters) thatare based on the wireless device information. The base station DU mayforward (e.g., without interpreting, without decoding, etc.), to thewireless device which may receive, the second RRC message (e.g., withoutinterpretation and/or decoding of the second RRC message). The wirelessdevice may send, to the base station DU and based on a powerconfiguration parameter (e.g., the at least one power configurationparameter and/or one or more other power configuration parameters), atleast one transport block. The base station CU may determine at leastone configuration parameter for at least a second wireless device (e.g.,which may include the wireless device and one or more additionalwireless devices). The base station CU may send, to the base station DUwhich may receive, a third message comprising that at least oneconfiguration parameter for at least a second wireless device. The basestation DU may forward (e.g., without interpreting, without decoding,etc.), to the at least the second wireless device, the third messagecomprising the at least one configuration parameter for the at least thesecond wireless device.

FIG. 23 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 120A and/or 120B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 2300 may include one ormore processors 2301, which may execute instructions stored in therandom access memory (RAM) 2303, the removable media 2304 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive2305. The computing device 2300 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 2301 andany process that requests access to any hardware and/or softwarecomponents of the computing device 2300 (e.g., ROM 2302, RAM 2303, theremovable media 2304, the hard drive 2305, the device controller 2307, anetwork interface 2309, a GPS 2311, a Bluetooth interface 2312, a Wi-Fiinterface 2313, etc.). The computing device 2300 may include one or moreoutput devices, such as the display 2306 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 2307, such as a video processor. There mayalso be one or more user input devices 2308, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device2300 may also include one or more network interfaces, such as a networkinterface 2309, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 2309 may provide aninterface for the computing device 2300 to communicate with a network2310 (e.g., a RAN, or any other network). The network interface 2309 mayinclude a modem (e.g., a cable modem), and the external network 2310 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 2300 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 2311, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 2300.

The example in FIG. 23 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 2300 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 2301, ROM storage 2302, display 2306, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 23.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, Wi-Fi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

What is claimed is:
 1. A method comprising: sending, by a wirelessdevice to a base station distributed unit (DU), a first radio resourcecontrol (RRC) message comprising an indication of a power configurationfor the wireless device; receiving, by the wireless device from a basestation central unit (CU) via the base station DU, a second RRC messagecomprising at least one power configuration parameter, wherein the atleast one power configuration parameter is based on the indication; andsending, to the base station DU and based on the at least one powerconfiguration parameter, at least one transport block.
 2. The method ofclaim 1, wherein the power configuration for the wireless devicecomprises a power preference indication indicating that the wirelessdevice prefers a configuration for power saving.
 3. The method of claim1, wherein the receiving the second RRC message comprises receiving thesecond RRC message forwarded by the base station DU from the basestation CU.
 4. The method of claim 1, wherein the at least one powerconfiguration parameter is determined by the base station DU based onthe indication of the power configuration for the wireless device. 5.The method of claim 1, wherein the first RRC message further comprisesat least one of: random access information, connection establishmentfailure information, bandwidth preference information, radio linkmonitoring information, a logged measurement result, or mobility historyinformation.
 6. The method of claim 1, further comprising: sending, bythe wireless device to the base station DU, one or more random accesspreambles.
 7. The method of claim 1, wherein the second RRC messagefurther comprises at least one of: a multicast-broadcast singlefrequency network (MBSFN) configuration parameter, a beamformingconfiguration parameter, a bandwidth part (BWP) configuration parameter,or a frequency configuration parameter.
 8. The method of claim 1,further comprising: determining, by the wireless device, wireless deviceinformation comprising the indication of the power configuration for thewireless device, wherein the first RRC message comprises the wirelessdevice information.
 9. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: send, to a basestation distributed unit (DU), a first radio resource control (RRC)message comprising an indication of a power configuration for thewireless device; receive, from a base station central unit (CU) via thebase station DU, a second RRC message comprising at least one powerconfiguration parameter, wherein the at least one power configurationparameter is based on the indication; and send, to the base station DUand based on the at least one power configuration parameter, at leastone transport block.
 10. The wireless device of claim 9, wherein thepower configuration for the wireless device comprises a power preferenceindication indicating that the wireless device prefers a configurationfor power saving.
 11. The wireless device of claim 9, wherein theinstructions, when executed by the one or more processors, cause thewireless device to receive the second RRC message by receiving thesecond RRC message forwarded by the base station DU from the basestation CU.
 12. The wireless device of claim 9, wherein the at least onepower configuration parameter is determined by the base station DU basedon the indication of the power configuration for the wireless device.13. The wireless device of claim 9, wherein the first RRC messagefurther comprises at least one of: random access information, connectionestablishment failure information, bandwidth preference information,radio link monitoring information, a logged measurement result, ormobility history information.
 14. The wireless device of claim 9,wherein the instructions, when executed by the one or more processors,further cause the wireless device to: send, to the base station DU, oneor more random access preambles.
 15. The wireless device of claim 9,wherein the second RRC message further comprises at least one of: amulticast-broadcast single frequency network (MBSFN) configurationparameter, a beamforming configuration parameter, a bandwidth part (BWP)configuration parameter, or a frequency configuration parameter.
 16. Thewireless device of claim 9, wherein the instructions, when executed bythe one or more processors, further cause the wireless device to:determine wireless device information comprising the indication of thepower configuration for the wireless device, wherein the first RRCmessage comprises the wireless device information.
 17. A non-transitorycomputer-readable medium storing instructions that, when executed,configure a wireless device to: send, to a base station distributed unit(DU), a first radio resource control (RRC) message comprising anindication of a power configuration for the wireless device; receive,from a base station central unit (CU) via the base station DU, a secondRRC message comprising at least one power configuration parameter,wherein the at least one power configuration parameter is based on theindication; and send, to the base station DU and based on the at leastone power configuration parameter, at least one transport block.
 18. Thenon-transitory computer-readable medium of claim 17, wherein the powerconfiguration for the wireless device comprises a power preferenceindication indicating that the wireless device prefers a configurationfor power saving.
 19. The non-transitory computer-readable medium ofclaim 17, wherein the instructions, when executed, configure thewireless device to receive the second RRC message by receiving thesecond RRC message forwarded by the base station DU from the basestation CU.
 20. The non-transitory computer-readable medium of claim 17,wherein the at least one power configuration parameter is determined bythe base station DU based on the indication of the power configurationfor the wireless device.
 21. The non-transitory computer-readable mediumof claim 17, wherein the first RRC message further comprises at leastone of: random access information, connection establishment failureinformation, bandwidth preference information, radio link monitoringinformation, a logged measurement result, or mobility historyinformation.
 22. The non-transitory computer-readable medium of claim17, wherein the instructions, when executed, further configure thewireless device to: send, to the base station DU, one or more randomaccess preambles.
 23. The non-transitory computer-readable medium ofclaim 17, wherein the second RRC message further comprises at least oneof: a multicast-broadcast single frequency network (MBSFN) configurationparameter, a beamforming configuration parameter, a bandwidth part (BWP)configuration parameter, or a frequency configuration parameter.
 24. Thenon-transitory computer-readable medium of claim 17, wherein theinstructions, when executed, further configure the wireless device to:determine wireless device information comprising the indication of thepower configuration for the wireless device, wherein the first RRCmessage comprises the wireless device information.